Nebula 2/Nebula Two.iso/SourceCode/MiscKit1.7.1/MiscKitArchive.mbox/mbox/000179_misckit-reques…aska.et.byu.edu_Sat Apr 9 22:51 MDT 1994.msg

Internet Message Format | 1994-10-30 | 4KB

Received: from yvax1.byu.edu by alaska.et.byu.edu; Sat, 9 Apr 1994 22:51:40 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-7 #4169)
 id <[e-mail]>; Sat, 9 Apr 1994 22:51:44 MST
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-7 #4169)
 id <[e-mail]>; Sat, 9 Apr 1994 22:51:38 MDT
Received: from yvax1.byu.edu by alaska.et.byu.edu; Sat,
 9 Apr 1994 22:49:35 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-7 #4169)
 id <[e-mail]>; Sat, 9 Apr 1994 22:49:37 MST
Received: from mercury.mcs.com by yvax.byu.edu (PMDF V4.3-7 #4169)
 id <[e-mail]>; Sat, 9 Apr 1994 22:49:33 MDT
Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.1)
 id <[e-mail]>; Sat, 9 Apr 94 23:50 CDT
Received: by katsun.chi.il.us (8.6.8/BK-1.10) id XAA07902; Sat,
 9 Apr 1994 23:48:57 -0500
Date: Sat, 09 Apr 1994 23:48:57 -0500
From: [e-mail] (Brian Katzung)
Subject: Re:  NeXT Mail from the Command Line
To: [e-mail], [e-mail], [e-mail],
        [e-mail], [e-mail],
        [e-mail], [e-mail],
        [e-mail], [e-mail]
Message-id: <[e-mail]>
Content-transfer-encoding: 7BIT
Status: RO

> From: "Zacharias J. Beckman" <[e-mail]>
> Date: Fri, 8 Apr 94 14:44:07 -0700
>
> Enclosed is a copy of my latest revision to the nextmail script, a cool
> command-line utility that will allow you to send NeXT Mail from any
> relatively standard UNIX system.  [...]
>
> Everything arrives as a NeXT Mail attachment with the filename next to it.

I also have tools to do this sort of things.  I have a Bourne shell version
that I have been using for some time, and a perl translation that I did
today.  The shell version isn't as transparent (because it uses "echo" for
output), and thus requires a little extra attention on the part of the user
during message composition.

Here are some of the differences between my tools and Zacharias':

- They work as filters, so there is a slight convenience/flexibility
  trade-off.  You can use them with Sun's "editheaders" option of
  /usr/ucb/mail, or see the results before you ship the mail.  You
  have to pass the result to "sendmail -t" or whatever as a separate
  step.

- You can compose an actual message with imbedded attachments, rather
  than just bundling attachments together with no text.  The filter
  provides the basic RTF boilerplate, and the user only needs to use a
  few simple rules to generate simple RTF bodies.  The necessary info
  is included in the introductory comments of each tool.  There is
  nothing to prevent you from using full RTF if you want to.

- As result of the previous two characteristics, you get full use of
  to:, cc:, and bcc: lines (or any other headers you may wish to use,
  such as reply-to:).

- Although my scripts also "gather" attachments distributed across
  multiple directories and make them appear to be all in one tree, the
  attachments are only duplicated once (in the tar archive) rather than
  twice (in the scratch directory AND the tar archive).  This reduces
  both the time and space required to run.  (There is a trade-off however;
  you may have to specify complete paths to attachments more often if your
  version of tar does not always return to the original directory properly
  after a "-C" flag.)

- No brief messages from the sponsor.  :-)

If you would like copies of my scripts, please reply by mail.  If you
don't indicate which version(s) you want or whether you can accept NeXT
mail, I will send both versions as a text message.

  -- Brian Katzung